Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1795

reference: 247-tree-1
name: 1795
tree-preservation-order: undefined
247-tpo-1
uprn
address-text
point: POINT (-1.000834 50.855732)
geometry: MULTIPOLYGON (((-1.000777 50.855726,-1.000780 50.855737,-1.000787 50.855748,-1.000800 50.855756,-1.000816 50.855761,-1.000833 50.855763,-1.000851 50.855761,-1.000867 50.855756,-1.000879 50.855748,-1.000888 50.855738,-1.000891 50.855727,-1.000888 50.855716,-1.000880 50.855706,-1.000868 50.855698,-1.000852 50.855693,-1.000835 50.855691,-1.000817 50.855692,-1.000801 50.855697,-1.000788 50.855705,-1.000780 50.855715,-1.000777 50.855726)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL